Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@cueweb/app/api/job/getdepends/route.ts`:
- Line 37: The code dereferences responseData.data without guarding for missing
data; update the dependsArray assignment to guard the whole chain (e.g., use
responseData?.data?.depends?.depends || []) so that when responseData or
responseData.data is missing the route returns an empty array instead of
throwing; modify the line that defines dependsArray to use optional chaining on
responseData and data (refer to the dependsArray variable and responseData
object).
- Around line 27-31: Remove the redundant JSON stringify/parse round-trip and
guard against malformed/empty bodies by wrapping await request.json() in a
try/catch; parse into jsonBody (e.g., const jsonBody = await request.json())
inside the try, validate that jsonBody is an object (typeof jsonBody ===
'object' && jsonBody !== null'), and on error or invalid body return
NextResponse.json({ error: 'Invalid request body' }, { status: 400 }); update
the code around jsonBody in route.ts to use this validated value.

In `@cueweb/components/ui/job-dependency-graph.tsx`:
- Around line 110-117: The graph state isn't cleared when a fetch returns no
dependencies, because setNodes/setEdges are only invoked inside the
rawNodes.size > 0 branch; update the logic around getLayoutedElements so that
when rawNodes.size === 0 (or the fetch errors) you explicitly clear state by
calling setNodes([]) and setEdges([]) and also ensure you clear nodes/edges
early when job.id changes (before/when starting the fetch) so the previous graph
won't persist; modify the code that uses rawNodes/rawEdges/getLayoutedElements
and the fetch-handling path to call setNodes([])/setEdges([]) on empty results
or failure.

---

Nitpick comments:
In `@cueweb/app/jobs/columns.tsx`:
- Line 27: The import FramesLayersPopup is unused in the module; remove the
import line "FramesLayersPopup" from the imports in this file (or if the
component was intended to be used, add the appropriate JSX reference to
FramesLayersPopup where needed). Update imports so no unused symbol remains.

In `@cueweb/components/ui/job-dependency-graph.tsx`:
- Around line 17-34: The bug is that the module-level dagreGraph variable
retains nodes between calls; change getLayoutedElements to instantiate a new
dagre.graphlib.Graph() inside the function (instead of using the shared
dagreGraph), call setDefaultEdgeLabel and setGraph on that local graph, then use
that local graph for setNode, setEdge and dagre.layout to ensure each layout
call starts with a fresh graph; update/remove references to the module-level
dagreGraph so all layout logic uses the local variable in getLayoutedElements.
- Around line 60-125: The effect currently re-fetches dependencies whenever
resolvedTheme changes because resolvedTheme is in the dependency array; change
this by splitting data fetch and theme-dependent styling: keep the data-loading
effect keyed only on job.id (the useEffect that calls loadGraph which uses
getDependsForJob and populates rawNodes/rawEdges then calls setNodes/setEdges)
so it only fetches once per job, and remove resolvedTheme from that effect’s
deps; then derive node/edge styles on theme changes separately (e.g., a useMemo
or a second effect that maps over the cached nodes/edges and updates their style
based on resolvedTheme) so you only recolor nodes without calling
getDependsForJob again.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@cueweb/components/ui/app-sidebar.tsx`:
- Around line 499-505: The button toggle that uses role="switch" (the element
that calls toggleGraph and reads showGraph) should not also expose aria-pressed;
remove the aria-pressed={showGraph} attribute so the control uses a single ARIA
state model (role="switch" with aria-checked={showGraph}) to match the expanded
version and avoid conflicting semantics.

In `@cueweb/components/ui/job-dependency-graph.tsx`:
- Around line 85-102: The responses returned by silentGetDepends and
silentGetWhatDependsOnThis may contain snake_case keys (e.g., depend_er_job)
while downstream code (ingestDepend in the dependency walker /
view-dependencies-dialog logic) expects camelCase (dependErJob); update
silentGetDepends and silentGetWhatDependsOnThis to normalize each Depend row to
the camelCase shape before returning (map over seq and copy/rename depend_er_job
-> dependErJob, any other snake_case aliases used by the API to their camelCase
counterparts), so the graph-building and ingestDepend callers always receive the
canonical field names regardless of gateway build.

In `@cueweb/components/ui/job-details-inline.tsx`:
- Around line 305-325: JobDependencyGraph is rendered without the onNodeNavigate
prop so node clicks fall back to router.push and leave the current Layers &
Frames detail view; update the JobDependencyGraph usage to pass an
onNodeNavigate callback that either selects the clicked job in-place (e.g., call
the parent selection handler with the job id/name) or routes to the
layers/frames tab for that job. Locate the JobDependencyGraph component
instantiation in job-details-inline.tsx and add a prop onNodeNavigate={(node) =>
{ /* select job or navigate to ?tab=layers or ?tab=frames for node.id */ }},
ensuring you use the same job selection/navigation functions used elsewhere in
this component to preserve in-place selection behavior instead of the global
router.push fallback.